Re: forward name resolution OK, but reverse doesn't work ...

2011-06-18 Thread Anand Buddhdev
On 18/06/2011 02:54, Mark Andrews wrote: Actually, the root name servers still serve ARPA. They only dropped IN-ADDR.ARPA earlier this year. However, anyone who runs the kind of configuration that Thomas has should be more vigilant. I would even recommend against slaving the root zone and the arp

Re: forward name resolution OK, but reverse doesn't work ...

2011-06-18 Thread Thomas Schweikle
Am 17.06.2011 23:29, schrieb Eivind Olsen: > Thomas Schweikle wrote: > >> But not reverse: >> !user@ks1:~$ host 74.125.79.99 >> !Host 99.79.125.74.in-addr.arpa not found: 2(SERVFAIL) > > ... > >> !zone "in-addr.arpa" { >> ! type slave; >> ! file "/var/cache/named/root/in-addr.arpa.slave"; >> !

Re: forward name resolution OK, but reverse doesn't work ...

2011-06-18 Thread David Sparro
On 6/17/2011 12:44 PM, Thomas Schweikle wrote: !zone "in-addr.arpa" { ! type slave; ! file "/var/cache/named/root/in-addr.arpa.slave"; ! masters { 192.5.5.241; }; ! notify no; !}; You're configuring you server to be authoritative for the reverse DNS zone. It's only going to have the rever

Re: forward name resolution OK, but reverse doesn't work ...

2011-06-18 Thread Thomas Schweikle
Am 18.06.2011 02:54, schrieb Mark Andrews: > The root servers no longer serve arpa or in-addr.arpa. > > See the following for where to transfer these zones from > now. http://seclists.org/nanog/2011/Feb/1453 Arr! Seems I'd overlooked that ... :-( I've corrected my config file. Now it wo

Re: forward name resolution OK, but reverse doesn't work ...

2011-06-18 Thread Mark Andrews
The root servers no longer serve arpa or in-addr.arpa. See the following for where to transfer these zones from now. http://seclists.org/nanog/2011/Feb/1453 Mark In message <4dfb848a.1080...@vr-web.de>, Thomas Schweikle writes: > This is a MIME-formatted message. If you see this text it means

Re: forward name resolution OK, but reverse doesn't work ...

2011-06-17 Thread Eivind Olsen
Thomas Schweikle wrote: > But not reverse: > !user@ks1:~$ host 74.125.79.99 > !Host 99.79.125.74.in-addr.arpa not found: 2(SERVFAIL) ... > !zone "in-addr.arpa" { > ! type slave; > ! file "/var/cache/named/root/in-addr.arpa.slave"; > ! masters { 192.5.5.241; }; > ! notify no; > !}; You seem

Re: forward name resolution OK, but reverse doesn't work ...

2011-06-17 Thread Lyle Giese
On 06/17/11 11:44, Thomas Schweikle wrote: Hi! I am having some problem with my nameserver: It resolves forward: !user@ks1:~$ host google.com !google.com has address 74.125.79.147 !google.com has address 74.125.79.99 !google.com has address 74.125.79.104 !google.com mail is handled by 50 alt4.a