[ODLPARENT-35] ODL won't boot correctly if dead DNS server is present. Created: 02/Jun/16  Updated: 24/Jan/18

Status: Open
Project: odlparent
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Jozef Behran Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 5991

 Description   

1. cat /etc/resolv.conf
2. Using IPTABLES cut each IP address reported in step 1 so that
traffic sent to them is silently dropped.
3. /where/your/odl/is/located/bin/start

These "step 2" actions could also work but they were not tested:

  • Cut only one DNS IP address, make the rest inaccessible (connection
    refused or so on).
  • Configure a DNS server that takes 2 minutes to provide any data.

The symptoms are that the ODL takes significantly longer to boot and the karaf console becomes inacessible (attempt to connect to the karaf console will result in opened connection whose other end does not respond to anything).

 Comments   
Comment by Robert Varga [ 31/Oct/16 ]

This can actually be a lot of things, as for example InetAddress resolves names in certain usage.

Generated at Wed Feb 07 20:27:26 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.