DNS Not Working

Discussion in 'ISPConfig 3 Priority Support' started by yupthatguy, Nov 5, 2021.

  1. yupthatguy

    yupthatguy Member

    The cause of my most recent confusion seems to be DNS configs not working correctly so my vbox test server cannot reach outside internet via the bridged network adapter.

    Under System >> server config >> nameservers I have:

    8.8.8.8,8.8.4.4,100.100.2.136,100.100.2.138

    However, when I check #cat /etc/resolv.conf, I get:
    Code:
    # cat /etc/resolv.conf
    # Generated by resolvconf
    search hitronhub.home example.com
    nameserver 192.168.0.1
    nameserver 61.31.233.1
    nameserver 61.31.1.1
    
    How can I solve this problem... outside internet is useful :)
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Edit the resolv.conf manually and test if it works then.
     
  3. yupthatguy

    yupthatguy Member

    ok... my /etc/resolv.conf now contains:

    Code:
    # cat /etc/resolv.conf
    # Generated by resolvconf
    search hitronhub.home example.com
    nameserver 192.168.0.1
    nameserver 61.31.233.1
    nameserver 61.31.1.1
    nameserver 8.8.8.8
    nameserver 8.8.4.4
    nameserver 100.100.2.136
    
    (the same is in the ispc gui)

    No internet.. do I need to restart resolvconf somehow? I tried:

    #systemctl restart resolvconf

    Didn't work..
     
  4. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    If your host can not reach Internet, it is not a problem with DNS. Can you ping those name server hosts, for example?
    Exactly what did not work? How do you determine it is not working?
     
  5. yupthatguy

    yupthatguy Member

    The host (ubuntu) has internet.... I can ping the guest ip from the host... I can ssh into the guest... the guest cannot reach outside internet..
    On the host, I can successfully ping 8.8.8.8

    My WP debug log was the first clue, couldn't reach wordpress, then tried #apt update can't connect to anything... Then I checked the manual...
     
  6. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    So the quest can not ping 8.8.8.8?
     
  7. yupthatguy

    yupthatguy Member

    Correct the guest (debian 10.5 test server) cannot ping 8.8.8.8
     
  8. yupthatguy

    yupthatguy Member

    Code:
    # ping 8.8.8.8
    PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
    From 192.168.1.84 icmp_seq=1 Destination Host Unreachable
    From 192.168.1.84 icmp_seq=2 Destination Host Unreachable
    From 192.168.1.84 icmp_seq=3 Destination Host Unreachable
    From 192.168.1.84 icmp_seq=4 Destination Host Unreachable
     
  9. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    So it is not a DNS problem.
    Do other quests work? In what way is this quest different?
     
  10. yupthatguy

    yupthatguy Member

    Confused.. The guest cannot ping 8.8.8.8 (or any other domain)

    I also have an ubuntu guest vm that I use for update tests... it can ping 8.8.8.8
     
  11. till

    till Super Moderator Staff Member ISPConfig Developer

    As @Taleman mentioned already, you do not have a DNS problem. When you can't ping an IP, then it's a network or routing problem or a Firewall issue but not a DNS issue.
     
  12. yupthatguy

    yupthatguy Member

    fair enough... you guys are the experts.. I just noticed the that /etc/resolv.conf info was different from system >> server config >> namerserver and in the manual it says the information should be the same. hence my confusion.

    Any advice on how I can restore internet access to the guest machine?

    the current guest is a ddrescue restore of a corrupted vdi. After successful restore, I performed these steps that enabled my network interfaces to work.

    additional info:
    #ifconfig -a
    (located new interface name)
    "eth8"

    #nano /etc/network/interfaces
    (replaced "eth-old" with "eth8")

    #ifconfig "eth8" down && ifconfig "eth8" up

    #reboot

    Am I missing something?
     
  13. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    So this guest runs as virtual machine on some virtualization system? If you restored the disk image from somewhere else or some other guest, check what the MAC address of the network adapter is, it may be the virtualization system must be configured to use that MAC for that guest.
    If that does not solve it, debug on the virtualization system the network connection to that guest.
     
  14. yupthatguy

    yupthatguy Member

    ok, will do.. thanks for the pointer
     
  15. yupthatguy

    yupthatguy Member

    Sometimes pointers really really help... back online.. time to build something... thanks fellas
     

Share This Page