Trouble with reverse DNS

Thomas Schulz schulz at
Sat Dec 15 22:31:58 UTC 2007

In article <fjvkpc$1juf$1 at>, Alan Clegg  <Alan_Clegg at> wrote:
>Thomas Schulz wrote:
>> We are switching internet service providers and are having trouble
>> getting the reverse DNS set up correctly.  Our new provider,
>> TDS Metrocom, claims to have set up their end correctly.  I believe
>> that I have set up my end correctly.  Could someone who knows what
>> they are doing take a look?  The address are through
>>  I have our server,, serving up
>> zone  I believe I have it set up
>> correctly.  I would appreciate any help.
>Looks like TDS forgot a "." in the delegation:
>[root at fatb ~]# dig @NS.TDS.NET. ns
>; <<>> DiG 9.4.2 <<>> @NS.TDS.NET. ns
>; (1 server found)
>;; global options:  printcmd
>;; Got answer:
>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58735
>;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0
>;; WARNING: recursion requested but not available
>; IN    NS
> 43200 IN NS
> 43200 IN NS

I saw those strange records and asked them about that.  They answered that  they
added the records the same way they added them for everyone else and that they
were correct.  I suspect that they did not read my email very closely.  I had
not realized that a missing '.' could do that until you pointed it out.  Now that
I think about it, I expect that that is what is wrong.  I will have to pound on
them Monday morning.

>I'm thinking that those NS records should be:
> 43200 IN NS
> 43200 IN NS
>Alan Clegg
>ISC Training and Support
>+1-650-423-1357 (o) +1-919-271-8851 (m)
Tom Schulz
schulz at

More information about the bind-users mailing list