dns error on exchange 2003 server 11166

[Jason Gallas]

I have no idea what could be causing this, the exchange server seems
to be working fine.

Error: 11166
The system failed to register host (A) resource records (RRs) for
network adapter
with settings:

Adapter Name : {6857346F-D99E-4F49-A108-2A1FB0A3E2BA}
Host Name : mail
Primary Domain Suffix : mydomain.com
DNS server list :
192.0.0.2, 192.0.0.1
Sent update to server : 192.0.0.2
IP Address(es) :
192.0.0.250

The reason the system could not register these RRs was because of a
security related problem. The cause of this could be (a) your computer
does not have permissions to register and update the specific DNS
domain name set for this adapter, or (b) there might have been a
problem negotiating valid credentials with the DNS server during the
processing of the update request.

You can manually retry DNS registration of the network adapter and
its settings by typing "ipconfig /registerdns" at the command prompt.
If problems still persist, contact your DNS server or network systems
administrator. For specific error

 

[Kevin D. Goodknecht Sr. [MVP]]

In

I have no idea what could be causing this, the exchange
server seems to be working fine.

Error: 11166
The system failed to register host (A) resource records
(RRs) for network adapter
with settings:

Adapter Name : {6857346F-D99E-4F49-A108-2A1FB0A3E2BA}
Host Name : mail
Primary Domain Suffix : mydomain.com
DNS server list :
192.0.0.2, 192.0.0.1
Sent update to server : 192.0.0.2
IP Address(es) :
192.0.0.250

The reason the system could not register these RRs was
because of a security related problem. The cause of this
could be (a) your computer does not have permissions to
register and update the specific DNS domain name set for
this adapter, or (b) there might have been a problem
negotiating valid credentials with the DNS server during
the processing of the update request.

You can manually retry DNS registration of the network
adapter and its settings by typing "ipconfig
/registerdns" at the command prompt. If problems still
persist, contact your DNS server or network systems
administrator. For specific error

The reason for the error is you are using a public address that belongs to
someone else. Change your IP scheme to a private address in 192.168.x.x
10.x.x.x or 172.16.x.x

 

[Jason Gallas]

On Thu, 26 Aug 2004 11:52:38 -0500, "Kevin D. Goodknecht Sr. [MVP]"

:In :Then Kevin replied below:
:> I have no idea what could be causing this, the exchange
:> server seems to be working fine.
:>
:> Error: 11166
:> The system failed to register host (A) resource records
:> (RRs) for network adapter
:> with settings:
:>
:> Adapter Name : {6857346F-D99E-4F49-A108-2A1FB0A3E2BA}
:> Host Name : mail
:> Primary Domain Suffix : mydomain.com
:> DNS server list :
:> 192.0.0.2, 192.0.0.1
:> Sent update to server : 192.0.0.2
:> IP Address(es) :
:> 192.0.0.250
:>
:> The reason the system could not register these RRs was
:> because of a security related problem. The cause of this
:> could be (a) your computer does not have permissions to
:> register and update the specific DNS domain name set for
:> this adapter, or (b) there might have been a problem
:> negotiating valid credentials with the DNS server during
:> the processing of the update request.
:>
:> You can manually retry DNS registration of the network
:> adapter and its settings by typing "ipconfig
:> /registerdns" at the command prompt. If problems still
:> persist, contact your DNS server or network systems
:> administrator. For specific error
:
:The reason for the error is you are using a public address that belongs to
:someone else. Change your IP scheme to a private address in 192.168.x.x
:10.x.x.x or 172.16.x.x
:
:--
:Best regards,
:Kevin D4 Dad Goodknecht Sr. [MVP]
:Hope This Helps
:================================================
Yes, but the addresses in question are on our private network and on
our own dns servers. We have never had a problem with this before.

 

[Kevin D. Goodknecht Sr. [MVP]]

In

Yes, but the addresses in question are on our private
network and on our own dns servers. We have never had a
problem with this before.

It is not relevant that the IP is on you private network, it is a public
address owned by IANA. You are using a public address scheme in your private
network and it is going to give you routing problems.

 

[Ace Fekay [MVP]]

In

It is not relevant that the IP is on you private network, it is a
public address owned by IANA. You are using a public address scheme
in your private network and it is going to give you routing problems.


--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
================================================

I believe the only problem he'll have is that he cannot get to those IP
addresses on the Internet. I know he should change the, for to use another
company's IP range for their own is really not, and with all due respect to
the original poster, "Internet community friendly" nor best business
practice or a best network design practice for that matter. FYI, here's who
it belongs to:
http://ws.arin.net/cgi-bin/whois.pl?queryinput=! NET-192-0-0-0-2

But as far as the errors, I think and am assuming that his router is
192.0.0.1, and unless its a Windows machine, then I'm going to also assume
that its a 3rd party router and that is the DNS address in the machine's IP
properties, so therefore, I believe its trying to register into the router.
If it 'worked' before, maybe it was always going to 192.0.0.2 and that
machine is now not responding, so its dropping down to the secondary entry,
which I'm assuming is the router.

Now these are all assumptions, since we don't have enough config and
topology info, and we'll need more info to confirm any assumptions.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.

 

[irwinutama]

Hi Jason,

You can refer to this document from MS : http://tinyurl.com/3rsxa

Hopefully this working.

*I have no idea what could be causing this, the exchange serve
seems
to be working fine.

Error: 11166
The system failed to register host (A) resource records (RRs) for
network adapter
with settings:

Adapter Name : {6857346F-D99E-4F49-A108-2A1FB0A3E2BA}
Host Name : mail
Primary Domain Suffix : mydomain.com
DNS server list :
192.0.0.2, 192.0.0.1
Sent update to server : 192.0.0.2
IP Address(es) :
192.0.0.250

The reason the system could not register these RRs was because of a
security related problem. The cause of this could be (a) you
computer
does not have permissions to register and update the specific DNS
domain name set for this adapter, or (b) there might have been a
problem negotiating valid credentials with the DNS server during the
processing of the update request.

You can manually retry DNS registration of the network adapter and
its settings by typing "ipconfig /registerdns" at the comman
prompt.
If problems still persist, contact your DNS server or networ
systems
administrator. For specific error

-
irwinutam

 

[Ace Fekay [MVP]]

In

Hi Jason,

You can refer to this document from MS : http://tinyurl.com/3rsxa

Hopefully this working.

Hi irwinutama

The article you posted, which is actually:

Clients cannot dynamically register DNS records in a single-label forward
lookup zone
http://support.microsoft.com/?id=826743

At first glance, doesn't seem to apply in this case, since the poster's
domain is not a single label name, unless he hid that from us.

Part of the issue with the registration issue for the original poster is
that Jason didn't give us enough configuration info to push forth on this.
Stuff that would have been helpful is an unedited ipconfig /all, the AD DNS
domain name, the zone name in DNS and whether updates (secure or not) are
enabled. The actual ipconfig /all would have helped us to see Jsaon's
Primary DNS Suffix, which is used in the registration process. I believe all
of that info would have given us a better starting point at diagnosing this

So, after re-reading the posts in this thread, I'm not sure how you came to
the conclusion that its a single label name issue based on the information
provided us in this thread.

Ace

PS.
Tinyurl is a great tool for really long URLs, but since this link isn't a
really long URL, with all due respect, it would have been helpful to see the
actual MS article ID number in the URL. I normally post the actual URL
along with the tinyurl if its a really long URL so everyone can see the both
the original and the short versions.