Grey delegation in dns
Hi experts,
I just add a new child domain to my parente domain.
But I have some dns issues.
In parent domain my child domain delegation appears grey in dns zone. (see greydns.jpg)
If I delete the child domain delegation and delegate again, I get this erros (see name-server-record01 and name-server-record02)
The parent domain and child domain are connected trought a vpn.
I use windows server 2008 R2 in both servers
Best regards
greydns.jpg
name-server-record01.jpg
name-server-record02.jpg
I just add a new child domain to my parente domain.
But I have some dns issues.
In parent domain my child domain delegation appears grey in dns zone. (see greydns.jpg)
If I delete the child domain delegation and delegate again, I get this erros (see name-server-record01 and name-server-record02)
The parent domain and child domain are connected trought a vpn.
I use windows server 2008 R2 in both servers
Best regards
greydns.jpg
name-server-record01.jpg
name-server-record02.jpg
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
From parent to child
C:\Users\Administrator>IPC
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
C:\Users\Administrator>pin
Pinging chld01 [169.254.66.135] with 32 bytes of data:
Reply from 169.254.169.148: Destination host unreachable.
Ping statistics for 169.254.66.135:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Control-C
^C
C:\Users\Administrator>pin
Pinging CHLD01 [192.168.2.101] with 32 bytes of data:
Reply from 192.168.2.101: bytes=32 time=24ms TTL=126
Reply from 192.168.2.101: bytes=32 time=24ms TTL=126
Reply from 192.168.2.101: bytes=32 time=24ms TTL=126
Reply from 192.168.2.101: bytes=32 time=23ms TTL=126
Ping statistics for 192.168.2.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 24ms, Average = 23ms
C:\Users\Administrator>pin
Pinging chld01.evora01.florasul.la
Reply from 192.168.2.101: bytes=32 time=23ms TTL=126
Reply from 192.168.2.101: bytes=32 time=25ms TTL=126
Reply from 192.168.2.101: bytes=32 time=23ms TTL=126
Reply from 192.168.2.101: bytes=32 time=23ms TTL=126
Ping statistics for 192.168.2.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 25ms, Average = 23ms
From child to parent
C:\Users\Administrator>ipc
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
C:\Users\Administrator>pin
Pinging dc01.florasul.lan [192.168.1.101] with 32 bytes of data:
Reply from 192.168.1.101: bytes=32 time=27ms TTL=126
Reply from 192.168.1.101: bytes=32 time=24ms TTL=126
Reply from 192.168.1.101: bytes=32 time=24ms TTL=126
Reply from 192.168.1.101: bytes=32 time=24ms TTL=126
Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 27ms, Average = 24ms
C:\Users\Administrator>pin
Pinging dc01.florasul.lan [192.168.1.101] with 32 bytes of data:
Reply from 192.168.1.101: bytes=32 time=25ms TTL=126
Reply from 192.168.1.101: bytes=32 time=24ms TTL=126
Reply from 192.168.1.101: bytes=32 time=23ms TTL=126
Reply from 192.168.1.101: bytes=32 time=25ms TTL=126
Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 25ms, Average = 24ms
C:\Users\Administrator>IPC
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
C:\Users\Administrator>pin
Pinging chld01 [169.254.66.135] with 32 bytes of data:
Reply from 169.254.169.148: Destination host unreachable.
Ping statistics for 169.254.66.135:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
Control-C
^C
C:\Users\Administrator>pin
Pinging CHLD01 [192.168.2.101] with 32 bytes of data:
Reply from 192.168.2.101: bytes=32 time=24ms TTL=126
Reply from 192.168.2.101: bytes=32 time=24ms TTL=126
Reply from 192.168.2.101: bytes=32 time=24ms TTL=126
Reply from 192.168.2.101: bytes=32 time=23ms TTL=126
Ping statistics for 192.168.2.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 24ms, Average = 23ms
C:\Users\Administrator>pin
Pinging chld01.evora01.florasul.la
Reply from 192.168.2.101: bytes=32 time=23ms TTL=126
Reply from 192.168.2.101: bytes=32 time=25ms TTL=126
Reply from 192.168.2.101: bytes=32 time=23ms TTL=126
Reply from 192.168.2.101: bytes=32 time=23ms TTL=126
Ping statistics for 192.168.2.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 25ms, Average = 23ms
From child to parent
C:\Users\Administrator>ipc
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
C:\Users\Administrator>pin
Pinging dc01.florasul.lan [192.168.1.101] with 32 bytes of data:
Reply from 192.168.1.101: bytes=32 time=27ms TTL=126
Reply from 192.168.1.101: bytes=32 time=24ms TTL=126
Reply from 192.168.1.101: bytes=32 time=24ms TTL=126
Reply from 192.168.1.101: bytes=32 time=24ms TTL=126
Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 27ms, Average = 24ms
C:\Users\Administrator>pin
Pinging dc01.florasul.lan [192.168.1.101] with 32 bytes of data:
Reply from 192.168.1.101: bytes=32 time=25ms TTL=126
Reply from 192.168.1.101: bytes=32 time=24ms TTL=126
Reply from 192.168.1.101: bytes=32 time=23ms TTL=126
Reply from 192.168.1.101: bytes=32 time=25ms TTL=126
Ping statistics for 192.168.1.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 25ms, Average = 24ms
ASKER
Ok, situation point.
If I ping dc01 from child, he resolve to dc01.florasul.lan (parent), sounds good
If I ping chld01 from parente I get this
C:\Users\Administrator>pin
Pinging chld01 [169.254.66.135] with 32 bytes of data:
Reply from 169.254.169.148: Destination host unreachable.
Ping statistics for 169.254.66.135:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
If I ping CHLD01 from parente I get this
C:\Users\Administrator>pin
Pinging CHLD01 [192.168.2.101] with 32 bytes of data:
Reply from 192.168.2.101: bytes=32 time=24ms TTL=126
Reply from 192.168.2.101: bytes=32 time=24ms TTL=126
Reply from 192.168.2.101: bytes=32 time=24ms TTL=126
Reply from 192.168.2.101: bytes=32 time=23ms TTL=126
But not resolve to CHLD01.evora01.florasul.la
If I ping dc01 from child, he resolve to dc01.florasul.lan (parent), sounds good
If I ping chld01 from parente I get this
C:\Users\Administrator>pin
Pinging chld01 [169.254.66.135] with 32 bytes of data:
Reply from 169.254.169.148: Destination host unreachable.
Ping statistics for 169.254.66.135:
Packets: Sent = 1, Received = 1, Lost = 0 (0% loss),
If I ping CHLD01 from parente I get this
C:\Users\Administrator>pin
Pinging CHLD01 [192.168.2.101] with 32 bytes of data:
Reply from 192.168.2.101: bytes=32 time=24ms TTL=126
Reply from 192.168.2.101: bytes=32 time=24ms TTL=126
Reply from 192.168.2.101: bytes=32 time=24ms TTL=126
Reply from 192.168.2.101: bytes=32 time=23ms TTL=126
But not resolve to CHLD01.evora01.florasul.la
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thanks for the help and clarifications, thanks to you I learned more about the functioning of dns
ASKER
is there any command to test dns comunications between parent and child?