Re: wildcarding everything
In message <56561f93336c3146836fdde78316154653c...@springnet-ex.springnet.local >, "Ben Bridges" writes: > I found the parking name servers for three domain parking companies, and > every one of them returned a bogus address for my company's website (as > well as every "major" website that I tried, such as IBM, Cisco, Yahoo, > Google, and isc.org). So it certainly appears that they are in fact > doing some sort of wildcarding. Maybe they have some sort of special > arrangement with the domain registrars??? Yes. Lots of them *are* domain registrar and don't care about about meeting the standard. They do anything to reduce their costs. The don't care that some of the answers being returned are wrong and are being rejected. They don't care that programers have had to code around their lack of conformance. Domain parkers that do this are as bad as load balancer vendors that only handle A queries. Mark > > -Original Message- > > From: Scott Haneda [mailto:talkli...@newgeo.com]=20 > > Sent: Thursday, January 29, 2009 12:06 AM > > To: Mark Andrews > > Cc: Ben Bridges; > > Subject: Re: wildcarding everything=20 > >=20 > > On Jan 28, 2009, at 3:34 PM, Mark Andrews wrote: > >=20 > > > In message <30e0039f-b0fd-4322-b0e0-52eeefa76...@newgeo.com>, Scott=20 > > > Haneda writ > > > es: > > >> I can remove the entire DNS management, zone creation, and=20 > > deltion if=20 > > >> I wildcard. Any domain in which they enter in my clients ns's will=20 > > >> resolve automatically as soon as the whois updates. > > > > > > Actually you can't. You will end up returning answers that > > > will be rejected. If the registrar does any sort of checking > > > the registration will also be rejected. > >=20 > >=20 > > Ok, thanks. So with this, it is a safe estimation, all these=20 > > domain parking systems actually create DNS records on the fly=20 > > for their users? I can not imagine someone as large as=20 > > godaddy with such inferior support, and a rather terrible web=20 > > interface, actually getting this right most of the time. > > -- > > Scott > >=20 > >=20 -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: mark_andr...@isc.org ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
RE: wildcarding everything
I found the parking name servers for three domain parking companies, and every one of them returned a bogus address for my company's website (as well as every "major" website that I tried, such as IBM, Cisco, Yahoo, Google, and isc.org). So it certainly appears that they are in fact doing some sort of wildcarding. Maybe they have some sort of special arrangement with the domain registrars??? > -Original Message- > From: Scott Haneda [mailto:talkli...@newgeo.com] > Sent: Thursday, January 29, 2009 12:06 AM > To: Mark Andrews > Cc: Ben Bridges; > Subject: Re: wildcarding everything > > On Jan 28, 2009, at 3:34 PM, Mark Andrews wrote: > > > In message <30e0039f-b0fd-4322-b0e0-52eeefa76...@newgeo.com>, Scott > > Haneda writ > > es: > >> I can remove the entire DNS management, zone creation, and > deltion if > >> I wildcard. Any domain in which they enter in my clients ns's will > >> resolve automatically as soon as the whois updates. > > > > Actually you can't. You will end up returning answers that > > will be rejected. If the registrar does any sort of checking > > the registration will also be rejected. > > > Ok, thanks. So with this, it is a safe estimation, all these > domain parking systems actually create DNS records on the fly > for their users? I can not imagine someone as large as > godaddy with such inferior support, and a rather terrible web > interface, actually getting this right most of the time. > -- > Scott > > ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: wildcarding everything
On Jan 28, 2009, at 3:34 PM, Mark Andrews wrote: In message <30e0039f-b0fd-4322-b0e0-52eeefa76...@newgeo.com>, Scott Haneda writ es: I can remove the entire DNS management, zone creation, and deltion if I wildcard. Any domain in which they enter in my clients ns's will resolve automatically as soon as the whois updates. Actually you can't. You will end up returning answers that will be rejected. If the registrar does any sort of checking the registration will also be rejected. Ok, thanks. So with this, it is a safe estimation, all these domain parking systems actually create DNS records on the fly for their users? I can not imagine someone as large as godaddy with such inferior support, and a rather terrible web interface, actually getting this right most of the time. -- Scott ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: wildcarding everything
In message <30e0039f-b0fd-4322-b0e0-52eeefa76...@newgeo.com>, Scott Haneda writ es: > I can remove the entire DNS management, zone creation, and deltion if > I wildcard. Any domain in which they enter in my clients ns's will > resolve automatically as soon as the whois updates. Actually you can't. You will end up returning answers that will be rejected. If the registrar does any sort of checking the registration will also be rejected. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: mark_andr...@isc.org ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: wildcarding everything
Excuse any spelling. I'm mobile. I would be wildcarding "." My client has a website building service. You get a free account and tools to get your site online all built in a browser with web based tools. It works well now but the synchronization of the database with named, users coming and going, keeping a slave up to date, delete zones, all that is a burden. All the time the users need status of their domain. Where the whois is at, if their zone has been created etc. It works, they have growing pains. It us only in private test and growing fast. Free seems to be appealing :) Since users sign up they must change their ns's at their registrar. They own their domains. They can leave at any time. The service does not offer registration. I can remove the entire DNS management, zone creation, and deltion if I wildcard. Any domain in which they enter in my clients ns's will resolve automatically as soon as the whois updates. So yes, these two ns's would be authoritative for all domains, but if I understand it correct, only those that users so chose to. It's not like an end user would request amazon.com and ever hit these two ns's. If that could happen DNS would be easily messed with. The ns's would deny recursion, they of course would not be used as a local resolved either. As a matter pf fact recursion would be denied to all nets entirely. I hope this explains it better. While this is not domain parking, it acts much like it, I would guess large registrars do something similar. I can not imagine them generating all these real zone files in such quantity for every parked domain. I'm trying to bring reliability in the synchronization of services trying to be offered. Thanks fly any suggestions. -- Scott Iphone says hello. On Jan 28, 2009, at 8:44 AM, "Ben Bridges" wrote: What specifically are you intending to wildcard? "com."? "net."? "."? If so, then you would be implicitly making your name servers authoritative for domains for which your servers are not supposed to be authoritative. Ben Bridges -Original Message- From: bind-users-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Scott Haneda Sent: Wednesday, January 28, 2009 3:31 AM To: bind-users@lists.isc.org Subject: wildcarding everything Hello, I am wondering the technical possibility of a DNS change. Even if it is technically possible, I also want to make sure it is compliant as well. I would like to resolve any and all requests to a fixed IP, if there is no zone in place. While I understand I can create a zone for *.example.com and resolve all of the * portion to an A record and further have a web server take over... What I am looking to do now, is have the very act of having my two NS's listed as NS's with their domain, resolve to an A record. Essentially, wildcard the entire DNS machine. There may be cases where a real zone is put in place, to a different A record, and that would need to take priority, but if it does not, I would like to resolve it. The NS's in question will not be answering for recursive queries, so I am not worried about local requests getting hijacked or mis-routed. An example would be: some-domain-foo.com is registered. My NS of ns-me.example.com is set up and working, but does not have some-domain-foo.com entered as a zone. When a request comes in for some-domain-foo.com I want an A record for an IP of my choice, also for www.some-domain-foo.com as well. Possible? Acceptable? Thanks. -- Scott ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
RE: wildcarding everything
What specifically are you intending to wildcard? "com."? "net."? "."? If so, then you would be implicitly making your name servers authoritative for domains for which your servers are not supposed to be authoritative. Ben Bridges > -Original Message- > From: bind-users-boun...@lists.isc.org > [mailto:bind-users-boun...@lists.isc.org] On Behalf Of Scott Haneda > Sent: Wednesday, January 28, 2009 3:31 AM > To: bind-users@lists.isc.org > Subject: wildcarding everything > > Hello, I am wondering the technical possibility of a DNS > change. Even if it is technically possible, I also want to > make sure it is compliant as well. > > I would like to resolve any and all requests to a fixed IP, > if there is no zone in place. While I understand I can > create a zone for *.example.com and resolve all of the * > portion to an A record and further have a web server take over... > > What I am looking to do now, is have the very act of having my two > NS's listed as NS's with their domain, resolve to an A record. > Essentially, wildcard the entire DNS machine. > > There may be cases where a real zone is put in place, to a > different A record, and that would need to take priority, but > if it does not, I would like to resolve it. > > The NS's in question will not be answering for recursive > queries, so I am not worried about local requests getting > hijacked or mis-routed. > > An example would be: > some-domain-foo.com is registered. My NS of ns-me.example.com > is set up and working, but does not have some-domain-foo.com > entered as a zone. When a request comes in for > some-domain-foo.com I want an A record for an IP of my > choice, also for www.some-domain-foo.com as well. > > Possible? Acceptable? > > Thanks. > -- > Scott > > ___ > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users > ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: wildcarding everything
If the dns only needs to resolve certain domains (you manage) and no other, it can be done Regards, Serge Fonville On Wed, Jan 28, 2009 at 1:11 PM, Alan Clegg wrote: > Scott Haneda wrote: > > > An example would be: > > some-domain-foo.com is registered. My NS of ns-me.example.com is set up > > and working, but does not have some-domain-foo.com entered as a zone. > > When a request comes in for some-domain-foo.com I want an A record for > > an IP of my choice, also for www.some-domain-foo.com as well. > > If I am the owner of said "some-domain-foo.com" and do not publish an A > record for every possible label within my zone, what right do YOU, a > person unknown to me, have to publish such records? > > No, not acceptable. Anything is possible. > > AlanC > > > ___ > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users > ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: wildcarding everything
Scott Haneda wrote: > An example would be: > some-domain-foo.com is registered. My NS of ns-me.example.com is set up > and working, but does not have some-domain-foo.com entered as a zone. > When a request comes in for some-domain-foo.com I want an A record for > an IP of my choice, also for www.some-domain-foo.com as well. If I am the owner of said "some-domain-foo.com" and do not publish an A record for every possible label within my zone, what right do YOU, a person unknown to me, have to publish such records? No, not acceptable. Anything is possible. AlanC signature.asc Description: OpenPGP digital signature ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
wildcarding everything
Hello, I am wondering the technical possibility of a DNS change. Even if it is technically possible, I also want to make sure it is compliant as well. I would like to resolve any and all requests to a fixed IP, if there is no zone in place. While I understand I can create a zone for *.example.com and resolve all of the * portion to an A record and further have a web server take over... What I am looking to do now, is have the very act of having my two NS's listed as NS's with their domain, resolve to an A record. Essentially, wildcard the entire DNS machine. There may be cases where a real zone is put in place, to a different A record, and that would need to take priority, but if it does not, I would like to resolve it. The NS's in question will not be answering for recursive queries, so I am not worried about local requests getting hijacked or mis-routed. An example would be: some-domain-foo.com is registered. My NS of ns-me.example.com is set up and working, but does not have some-domain-foo.com entered as a zone. When a request comes in for some-domain-foo.com I want an A record for an IP of my choice, also for www.some-domain-foo.com as well. Possible? Acceptable? Thanks. -- Scott ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
