Re: DNS weirdness

2002-02-07 Thread dave brett
I give up we have different views on how DNS should work. Thanks for your insight. david On Wed, 6 Feb 2002, David Talkington wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 dave brett wrote: Using the root servers defeats the purpose of the design of the whole structure.

Re: DNS weirdness

2002-02-07 Thread David Talkington
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 dave brett wrote: I give up we have different views on how DNS should work. Thanks for your insight. And thank you for the lively discussion. - -d - -- David Talkington PGP key: http://www.prairienet.org/~dtalk/0xCA4C11AD.pgp - --

Re: DNS Weirdness -nevermind

2002-02-06 Thread Gerry Doris
Well, that just shows once again that all the good names have already been picked...IBM.com, Microsoft.com, Dekkers.com... Gerry On Wed, 6 Feb 2002, Edward Dekkers wrote: After a bit of investigation, it seems someone had indeed registered dekkers.com way back in 1997. The record was

Re: DNS weirdness

2002-02-06 Thread dave brett
You should not be using the root servers. Instead use the DNS servers of your ISP. david On Tue, 5 Feb 2002, David Talkington wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Cameron Simpson wrote: On 09:16 06 Feb 2002, Edward Dekkers [EMAIL PROTECTED] wrote: | domain.com

Re: DNS weirdness

2002-02-06 Thread David Talkington
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 dave brett wrote: You should not be using the root servers. Instead use the DNS servers of your ISP. That isn't necessarily true, and is a long and sordid debate that I don't think you really want to open. ;-) The choice of DNS resolvers boils

Re: DNS weirdness

2002-02-06 Thread dave brett
Hi David Using the root servers defeats the purpose of the design of the whole structure. What I do if I don't like the ISP's DNS servers is use a different one, but not the root. The easiest way to look at it is, if everybody did it, what would the effect be? david On Wed, 6 Feb 2002, David

Re: DNS weirdness

2002-02-06 Thread David Talkington
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ok, so you _do_ want to open this discussion. I'll do my best, with the caveat that this is pre-espresso. Using the root servers defeats the purpose of the design of the whole structure. I'll respectfully suggest that I'm not able to find any

Re: DNS weirdness

2002-02-06 Thread dave brett
On Wed, 6 Feb 2002, David Talkington wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ok, so you _do_ want to open this discussion. I'll do my best, with the caveat that this is pre-espresso. I don't want to get into a long debate. I was just pointing out the design concept

Re: DNS weirdness

2002-02-06 Thread David Talkington
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 dave brett wrote: Using the root servers defeats the purpose of the design of the whole structure. I'll respectfully suggest that I'm not able to find any evidence in the RFC to support that conclusion. Read on ... I would not expect this

Re: DNS weirdness

2002-02-06 Thread David Talkington
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Talkington wrote: Remember that the roots _only_ answer queries for top-level namespaces. They are not recursive. That means (following my previous example) that even if every one of my workstations hits a redhat.com site every two minutes

Re: DNS Weirdness -nevermind

2002-02-06 Thread Edward Dekkers
Well, that just shows once again that all the good names have already been picked...IBM.com, Microsoft.com, Dekkers.com... Gerry LOL - and that's all I'll say about that. Looks like I've already started a DNS debate. Regards and thanks again. Edward.

DNS weirdness

2002-02-05 Thread Edward Dekkers
What the??? I have set up an internal domain 'domain.com' On this domain I have 5 PCs 1 Linux 6.2 (server.domain.com)(192.168.0.10) 2 My own PC (edward.domain.com)(192.168.0.2) 3 My wife's PC (kylie.domain.com)(DHCP - only just starting to test it - can drop it back to

RE: DNS weirdness

2002-02-05 Thread Mike Pelley
Of Edward Dekkers Sent: Tuesday, February 05, 2002 9:12 PM To: [EMAIL PROTECTED] Subject: DNS weirdness What the??? I have set up an internal domain 'domain.com' On this domain I have 5 PCs 1 Linux 6.2 (server.domain.com)(192.168.0.10) 2 My own PC (edward.domain.com)(192.168.0.2) 3 My

Re: DNS weirdness

2002-02-05 Thread Gerry Doris
On Wed, 6 Feb 2002, Edward Dekkers wrote: kylie or kylie.domain.com (216.147.69.55 --- Where did THIS come from). It says it is pinging from 203.59.196.224. OK, I thought maybe stuffed up my DHCP somehow, but it gets worse. PING responds EVEN with the PC turned OFF. How does that work???

Re: DNS weirdness

2002-02-05 Thread Gerry Doris
On Wed, 6 Feb 2002, Edward Dekkers wrote: What the??? I have set up an internal domain 'domain.com' domain.com belongs to a bank in Bethlehem, PA. Gerry -- The lyfe so short, the craft so long to learne Chaucer ___ Redhat-list mailing

Re: DNS weirdness

2002-02-05 Thread Edward Dekkers
domain.com belongs to a bank in Bethlehem, PA. sorry, domain.com was just the example I used Gerry. your first answer is the correct one. the real names I use in here are based on the domain dekkers.com. which is what worries me. They SHOULD NOT RESOLVE externally. I was hoping they would

Fw: DNS weirdness - MORE INFO

2002-02-05 Thread Edward Dekkers
Just noticed in my logs that when named starts up this is what happens: Feb 6 08:17:19 server named[8251]: hint zone (IN) loaded (serial 0) Feb 6 08:17:19 server named[8251]: Zone 0.0.127.in-addr.arpa (file named.local): No default TTL ($TTL value) set, using SOA minimum instead Feb 6

Re: Fw: DNS weirdness - MORE INFO

2002-02-05 Thread Devon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 05 February 2002 08:09 pm, Edward Dekkers wrote: Just noticed in my logs that when named starts up this is what happens: [snip] (eth0) Feb 6 08:17:19 server named[8251]: listening on [203.59.196.224].53 (ppp0) Feb 6 08:17:19 server

Re: DNS weirdness

2002-02-05 Thread Devon
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday 05 February 2002 08:16 pm, Edward Dekkers wrote: the real names I use in here are based on the domain dekkers.com. which is what worries me. They SHOULD NOT RESOLVE externally. I was hoping they would not. But, as you have found out,

Re: DNS weirdness

2002-02-05 Thread Ray Curtis
ed == Edward Dekkers [EMAIL PROTECTED] writes: domain.com belongs to a bank in Bethlehem, PA. ed sorry, domain.com was just the example I used Gerry. ed your first answer is the correct one. ed the real names I use in here are based on the domain dekkers.com. ed

DNS Weirdness -nevermind

2002-02-05 Thread Edward Dekkers
After a bit of investigation, it seems someone had indeed registered dekkers.com way back in 1997. The record was updated 28/12/2001, so I assume they've only just started using it and we just hadn't noticed up until now. (Although a few 'niggly' things now start to make sense) The guy who

Re: DNS weirdness

2002-02-05 Thread Cameron Simpson
On 09:16 06 Feb 2002, Edward Dekkers [EMAIL PROTECTED] wrote: | domain.com belongs to a bank in Bethlehem, PA. | | the real names I use in here are based on the domain dekkers.com. | | which is what worries me. They SHOULD NOT RESOLVE externally. I was hoping | they would not. But, as you

Re: Fw: DNS weirdness - MORE INFO

2002-02-05 Thread Edward Dekkers
How do I stop that? Tell it to stop. :) [root@tuxfan etc]# head -10 /etc/named.conf acl localnet { 192.168.0/24; 127.0.0.1/32; }; options { directory /var/named; allow-query { localnet; }; listen-on{ 192.168.0.3; 127.0.0.1; }; auth-nxdomain no;

Re: DNS weirdness

2002-02-05 Thread David Talkington
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Cameron Simpson wrote: On 09:16 06 Feb 2002, Edward Dekkers [EMAIL PROTECTED] wrote: | domain.com belongs to a bank in Bethlehem, PA. | | the real names I use in here are based on the domain dekkers.com. | | which is what worries me. They SHOULD

Re: DNS weirdness

2002-02-05 Thread David Talkington
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David Talkington wrote: Either register the domain or use a nonexistent top level domain like .home. Or use a split-horizon DNS resolver on your private network - one that's a) only visible to your machines, and b) obeys your authority for