Archived from groups: microsoft.public.win2000.dns (
More info?)
C:\WINDOWS>nslookup -debug -q=soa heaven.intercontinentbank.com
------------
Got answer:
HEADER:
opcode = QUERY, id = 1, rcode = NOERROR
header flags: response, auth. answer, want recursion, recursion
avail.
questions = 1, answers = 1, authority records = 0, additional = 0
QUESTIONS:
14.0.168.192.in-addr.arpa, type = PTR, class = IN
ANSWERS:
-> 14.0.168.192.in-addr.arpa
name = dc1.intercontinentbank.com
ttl = 900 (15 mins)
------------
Server: dc1.intercontinentbank.com
Address: 192.168.0.14
------------
Got answer:
HEADER:
opcode = QUERY, id = 2, rcode = NXDOMAIN
header flags: response, auth. answer, want recursion, recursion
avail.
questions = 1, answers = 0, authority records = 1, additional = 1
QUESTIONS:
heaven.intercontinentbank.com.intercontinentbank.com, type = SOA,
class = IN
AUTHORITY RECORDS:
-> intercontinentbank.com
ttl = 3600 (1 hour)
primary name server = dc1.intercontinentbank.com
responsible mail addr = admin.intercontinentbank.com
serial = 56440
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
ADDITIONAL RECORDS:
-> dc1.intercontinentbank.com
internet address = 192.168.0.14
ttl = 3600 (1 hour)
------------
------------
Got answer:
HEADER:
opcode = QUERY, id = 3, rcode = NXDOMAIN
header flags: response, auth. answer, want recursion, recursion
avail.
questions = 1, answers = 0, authority records = 1, additional = 1
QUESTIONS:
heaven.intercontinentbank.com.interservice.local, type = SOA, class
= IN
AUTHORITY RECORDS:
-> interservice.local
ttl = 3600 (1 hour)
primary name server = is000.interservice.local
responsible mail addr = admin
serial = 1631
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
ADDITIONAL RECORDS:
-> is000.interservice.local
internet address = 192.168.151.2
ttl = 1200 (20 mins)
------------
------------
Got answer:
HEADER:
opcode = QUERY, id = 4, rcode = NOERROR
header flags: response, auth. answer, want recursion, recursion
avail.
questions = 1, answers = 0, authority records = 1, additional = 1
QUESTIONS:
heaven.intercontinentbank.com, type = SOA, class = IN
AUTHORITY RECORDS:
-> intercontinentbank.com
ttl = 3600 (1 hour)
primary name server = dc1.intercontinentbank.com
responsible mail addr = admin.intercontinentbank.com
serial = 56440
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
ADDITIONAL RECORDS:
-> dc1.intercontinentbank.com
internet address = 192.168.0.14
ttl = 3600 (1 hour)
------------
intercontinentbank.com
ttl = 3600 (1 hour)
primary name server = dc1.intercontinentbank.com
responsible mail addr = admin.intercontinentbank.com
serial = 56440
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
dc1.intercontinentbank.com
internet address = 192.168.0.14
ttl = 3600 (1 hour)
"Jeff Westhead [MSFT]" <jwesth@online.microsoft.com> wrote in message
news:%23YvObPCcEHA.2520@TK2MSFTNGP12.phx.gbl...
> From the client try running this and pasting the output here.
>
> nslookup -debug -q=soa heaven.intercontinentbank.com.
>
> This is the query the client uses to locate a server to take the update.
>
> "Mykhaylo Khodorev" <ralfeus@chicagocentre.com.ua> wrote in message
> news:cdp10v$2t0s$1@news.dg.net.ua...
> > I've just found very strange event in my event log after an attempt to
> > manually register RR in DNS:
> > Event Type: Warning
> > Event Source: DnsApi
> > Event Category: None
> > Event ID: 11163
> > Date: 22.07.2004
> > Time: 21:05:58
> > User: N/A
> > Computer: HEAVEN
> > Description:
> > The system failed to register host (A) resource records (RRs) for
network
> > adapter
> > with settings:
> >
> > Adapter Name : {AA893F47-F664-46AE-A4BE-6634C952ADB0}
> > Host Name : heaven
> > Primary Domain Suffix : intercontinentbank.com
> > DNS server list :
> > 192.168.0.14
> > Sent update to server : 192.1.1.1
> > IP Address(es) :
> > 192.168.0.245
> >
> > The reason the system could not register these RRs was because the DNS
> > server failed the update request. The most likely cause of this is that
> the
> > authoritative DNS server required to process this update request has a
> lock
> > in place on the zone, probably because a zone transfer is in progress.
> >
> > 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 more information, see Help and Support Center at
> > http://go.microsoft.com/fwlink/events.asp.
> > Data:
> > 0000: 2d 23 00 00 -#..
> >
> > The issue that I don't have the address 192.1.1.1
> > I didn't find anywhere the value 192.1.1.1 Where from this address
> appeared?
> >
> >
>
>