Story #2802
cn nameserver inconsistency in sandbox
Start date:
Due date:
% Done:
100%
Story Points:
Sprint:
Description
the 3 cns in sandbox have 3 different nameserver listings.
History
#1 Updated by Rob Nahf almost 12 years ago
- Target version changed from Sprint-2012.19-Block.3.2 to Sprint-2012.21-Block.3.3
- Position deleted (
1) - Position set to 1
#2 Updated by Rob Nahf almost 12 years ago
- Assignee set to Chris Jones
#3 Updated by Dave Vieglais almost 12 years ago
Shouldn't be any impact from this unless the servers are failing. /etc/resolv.conf from production CNs looks like:
search dataone.org
nameserver 128.111.220.18
nameserver 174.37.196.55
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver 128.111.220.16
See also #2712
#4 Updated by Dave Vieglais almost 12 years ago
- Status changed from New to In Progress
- Assignee changed from Chris Jones to Dave Vieglais
#5 Updated by Dave Vieglais almost 12 years ago
There's a problem here.
Updating resolv.conf with the settings from production CNs causes look ups to fail for common domains such as google.com. Need to investigate this further.
#6 Updated by Dave Vieglais almost 12 years ago
- Status changed from In Progress to Closed
resolv.conf updated to match the production CNs. Original values preserved but commented in /etc/resolv.conf
