You are here

Name resolution (DNS) not working?

4 posts / 0 new
Last post
kenneth.hempkins
kenneth.hempkins's picture
Name resolution (DNS) not working?

Hi,

 

Downloaded the VM and got up and running - cool. I've set IP manually by logging in to console and ran "netconf". However, when doing autodiscovery, DNS-resolution isn't working. I was not able to activate with key either, and had to do a manual activation.

Trying to ping any hostname from console fails (ping ip works fine). As I am a network-admin and manges firewalls I know this is not an issue.

What am I missing?

(I dont' really know Linux, I'm a network admin, so please don't ask me to check stuff whitout proper instructions :) )

 

Cheers

Kenneth

smarsh
smarsh's picture
You need to setup DNS if its

You need to setup DNS if its not being assigned via DHCP - simply edit /etc/resolv.conf and add a line like:

nameserver 8.8.8.8

Where 8.8.8.8 is the IP of your internal DNS server. Then run 'dig hostname.yourdomain.com' to make sure it resolves :)

kenneth.hempkins
kenneth.hempkins's picture
Thanks a lot, that did the

Thanks a lot, that did the trick.

However, it's kind'a confusing that this is not done with "netconf" as it asks for DNS. Why does it ask for DNS servers if it's not used/updated properly?

Should perhaps be removed from "netconf" or make "netconf" update resolv.conf ?

Kenneth

smarsh
smarsh's picture
Hi Kenneth,

Hi Kenneth,

I've no idea bud - i havent used that tool personally, but if it doesnt work it sounds like a bug in the package supplied by the OS Vendor (ubuntu, i believe, in the virtual appliances case).

You could always try upgrading to the latest netconfig package to see if that works - but i would always advocate setting your network config / DNS servers via the command line; its daunting at first but once you get the hang of it, you gain a much greater understanding of what exactly is set, etc.

Cheers, and glad its working!

Sam