PC Review


Reply
Thread Tools Rate Thread

Curious about this DNS entry

 
 
=?Utf-8?B?Um9i?=
Guest
Posts: n/a
 
      21st Feb 2006
We have a W2k network here upgraded some time ago from NT4
There are x2 DC's, one of which is the internal network DNS server. Only
running fwd lookup zones.
I noticed on one of our member servers that there was a dnsapi entry in the
application log (event id 11157) where it could not update the PTR records.
OK no problem as there is no reverse lookup.
What did puzzle me was that it appears to have sent an update to 192.175.48.1.
I had a look further back in the archived logs and it has been doing this
for at least a year. This IP is 'pingable' and can be traced back to
prisoner.iana.org.
Can someone explain what this is about?
Thanks
 
Reply With Quote
 
 
 
 
Kevin D. Goodknecht Sr. [MVP]
Guest
Posts: n/a
 
      21st Feb 2006
Rob wrote:
> We have a W2k network here upgraded some time ago from NT4
> There are x2 DC's, one of which is the internal network DNS server.
> Only running fwd lookup zones.
> I noticed on one of our member servers that there was a dnsapi entry
> in the application log (event id 11157) where it could not update the
> PTR records. OK no problem as there is no reverse lookup.
> What did puzzle me was that it appears to have sent an update to
> 192.175.48.1. I had a look further back in the archived logs and it
> has been doing this
> for at least a year. This IP is 'pingable' and can be traced back to
> prisoner.iana.org.
> Can someone explain what this is about?
> Thanks


Since you don't have a reverse lookup zone, DNS clients that are trying to
register PTR records are sending updates to the internet server that holds
the Public SOA master server for the IP address. In you case, since it is in
a private IP address range, it goes to prisoner.iana.org.

If you will create a local reverse lookup zone on your DCs it will become
the local SOA master server, and it will take authority over the PTR record.


--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


 
Reply With Quote
 
=?Utf-8?B?Um9i?=
Guest
Posts: n/a
 
      21st Feb 2006
Thanks Kevin.
Is this coded into the networkservice then and not configurable?

"Kevin D. Goodknecht Sr. [MVP]" wrote:

> Rob wrote:
> > We have a W2k network here upgraded some time ago from NT4
> > There are x2 DC's, one of which is the internal network DNS server.
> > Only running fwd lookup zones.
> > I noticed on one of our member servers that there was a dnsapi entry
> > in the application log (event id 11157) where it could not update the
> > PTR records. OK no problem as there is no reverse lookup.
> > What did puzzle me was that it appears to have sent an update to
> > 192.175.48.1. I had a look further back in the archived logs and it
> > has been doing this
> > for at least a year. This IP is 'pingable' and can be traced back to
> > prisoner.iana.org.
> > Can someone explain what this is about?
> > Thanks

>
> Since you don't have a reverse lookup zone, DNS clients that are trying to
> register PTR records are sending updates to the internet server that holds
> the Public SOA master server for the IP address. In you case, since it is in
> a private IP address range, it goes to prisoner.iana.org.
>
> If you will create a local reverse lookup zone on your DCs it will become
> the local SOA master server, and it will take authority over the PTR record.
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> https://secure.lsaol.com/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>

 
Reply With Quote
 
Kevin D. Goodknecht Sr. [MVP]
Guest
Posts: n/a
 
      21st Feb 2006
Rob wrote:
> Thanks Kevin.
> Is this coded into the networkservice then and not configurable?


This is the way all DNS servers work. It does not matter what DNS server you
are using. If a DNS registration request is sent to a DNS server, the DNS
server will attempt to locate the Authoritative server for the record,
regardless of the record type, and send the update to that server. If it is
an A record, it will attempt to locate the Authoritative DNS for the domain
name. If it is a PTR, DNS will attempt to locate the Authoritative server
for the reverse lookup and send the PTR registration request to it.. Then
the DNS update is always sent to the Master server for the record. You
cannot change this, and it is why all AD integrated DNS zones will have the
its own name on the SOA Master server, to reduce cross network registration
requests.


>>> We have a W2k network here upgraded some time ago from NT4
>>> There are x2 DC's, one of which is the internal network DNS server.
>>> Only running fwd lookup zones.
>>> I noticed on one of our member servers that there was a dnsapi entry
>>> in the application log (event id 11157) where it could not update
>>> the
>>> PTR records. OK no problem as there is no reverse lookup.
>>> What did puzzle me was that it appears to have sent an update to
>>> 192.175.48.1. I had a look further back in the archived logs and it
>>> has been doing this
>>> for at least a year. This IP is 'pingable' and can be traced back
>>> to prisoner.iana.org.
>>> Can someone explain what this is about?
>>> Thanks

>>
>> Since you don't have a reverse lookup zone, DNS clients that are
>> trying to register PTR records are sending updates to the internet
>> server that holds the Public SOA master server for the IP address.
>> In you case, since it is in a private IP address range, it goes to
>> prisoner.iana.org.
>>
>> If you will create a local reverse lookup zone on your DCs it will
>> become the local SOA master server, and it will take authority over
>> the PTR record.





--
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
https://secure.lsaol.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


 
Reply With Quote
 
=?Utf-8?B?Um9i?=
Guest
Posts: n/a
 
      22nd Feb 2006
Thanks kevin you've been very helpful.

"Kevin D. Goodknecht Sr. [MVP]" wrote:

> Rob wrote:
> > Thanks Kevin.
> > Is this coded into the networkservice then and not configurable?

>
> This is the way all DNS servers work. It does not matter what DNS server you
> are using. If a DNS registration request is sent to a DNS server, the DNS
> server will attempt to locate the Authoritative server for the record,
> regardless of the record type, and send the update to that server. If it is
> an A record, it will attempt to locate the Authoritative DNS for the domain
> name. If it is a PTR, DNS will attempt to locate the Authoritative server
> for the reverse lookup and send the PTR registration request to it.. Then
> the DNS update is always sent to the Master server for the record. You
> cannot change this, and it is why all AD integrated DNS zones will have the
> its own name on the SOA Master server, to reduce cross network registration
> requests.
>
>
> >>> We have a W2k network here upgraded some time ago from NT4
> >>> There are x2 DC's, one of which is the internal network DNS server.
> >>> Only running fwd lookup zones.
> >>> I noticed on one of our member servers that there was a dnsapi entry
> >>> in the application log (event id 11157) where it could not update
> >>> the
> >>> PTR records. OK no problem as there is no reverse lookup.
> >>> What did puzzle me was that it appears to have sent an update to
> >>> 192.175.48.1. I had a look further back in the archived logs and it
> >>> has been doing this
> >>> for at least a year. This IP is 'pingable' and can be traced back
> >>> to prisoner.iana.org.
> >>> Can someone explain what this is about?
> >>> Thanks
> >>
> >> Since you don't have a reverse lookup zone, DNS clients that are
> >> trying to register PTR records are sending updates to the internet
> >> server that holds the Public SOA master server for the IP address.
> >> In you case, since it is in a private IP address range, it goes to
> >> prisoner.iana.org.
> >>
> >> If you will create a local reverse lookup zone on your DCs it will
> >> become the local SOA master server, and it will take authority over
> >> the PTR record.

>
>
>
>
> --
> Best regards,
> Kevin D. Goodknecht Sr. [MVP]
> Hope This Helps
> ===================================
> When responding to posts, please "Reply to Group"
> via your newsreader so that others may learn and
> benefit from your issue, to respond directly to
> me remove the nospam. from my email address.
> ===================================
> http://www.lonestaramerica.com/
> http://support.wftx.us/
> https://secure.lsaol.com/
> ===================================
> Use Outlook Express?... Get OE_Quotefix:
> It will strip signature out and more
> http://home.in.tum.de/~jain/software/oe-quotefix/
> ===================================
> Keep a back up of your OE settings and folders
> with OEBackup:
> http://www.oehelp.com/OEBackup/Default.aspx
> ===================================
>
>
>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Just curious =?Utf-8?B?TWly?= Microsoft Frontpage 21 25th Aug 2007 01:36 PM
Curious =?Utf-8?B?TWFya0I=?= Windows XP Work Remotely 1 10th Sep 2006 11:29 AM
Curious About Meaning of Error Log Entry DLKR Spyware Discussion 0 25th May 2005 06:07 PM
!Curious; possible bug... Max Burke Spyware Discussion 3 22nd Jan 2005 05:17 AM
Curious ! Gijomo Windows XP Help 1 3rd Apr 2004 04:25 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 08:43 AM.