Koozali.org: home of the SME Server

name resolution not working

John Da Silva

name resolution not working
« on: June 03, 2003, 04:26:10 PM »
I have setup SME 5.6 at ip 10.3.16.192 on my local network and am able to use my browser to access the server manager if I type in http://10.3.16.192/server-manager. I have also given the server the name "mmabatho". If I type in http://mmabatho I get "Page cannot be displayed".
My primary DNS server is at 10.3.0.192. I am not using a domain.

What am I doing wrong?  I am very new at Linux so I would require detailed instructions please.

Thank-you

Newbie

Re: name resolution not working
« Reply #1 on: June 03, 2003, 06:34:10 PM »
Do you have a Record in your dns sever setup to resolve the name "mmabatho"?

John Da Silva

Re: name resolution not working
« Reply #2 on: June 03, 2003, 07:34:13 PM »
Thanks for the reply

How do I check for this and if it is not there how do I insert a record?

Nathan Fowler

Re: name resolution not working
« Reply #3 on: June 03, 2003, 09:56:25 PM »
Be sure your clients are configured to use the IPaddress of mmabatho as their primary DNS server.  Also, if you login to your server try to ping "mmabatho" and it should resolve.

John Da Silva

Re: name resolution not working
« Reply #4 on: June 04, 2003, 02:34:27 AM »
If i "ping 10.3.16.192" i get a reply
If i "ping mmabatho" i get "Unknown host mmabatho"
I have set the prefered primary DNS on my machine to 10.3.16.192
My primary DNS is actually 10.3.0.192
Any ideas as to why?

Nathan Fowler

Re: name resolution not working
« Reply #5 on: June 04, 2003, 02:54:34 AM »
You may need to adjust your default suffix search order, the name "mmabatho" is actually a host on a domain, so without the FQDN completion or suffix search order you won't be able to resolve it without creating a HOSTS entry (%WINDIR%\SYSTEM32\DRIVERS\ETC\HOSTS)

Mike

Re: name resolution not working
« Reply #6 on: June 04, 2003, 08:36:19 AM »
Try setting the Default Gateway on the network card on the workstation to the address of the SME-Server 10.3.16.192 and select the address of the SME-Server as the Preferred DNS Server 10.3.16.192. You should then be able to ping the SME-Server IP address.
In your Web Browser under LAN settings Select Use a Proxy and enter the address of the SME-Server 10.3.16.192 going to port 3128 except Socks to port 1080.
You should then be able to access the Server Manager by entering the address http://mmabatho/server-manager/

Kevin

Re: name resolution not working
« Reply #7 on: August 12, 2003, 10:10:31 PM »
I have a similar problem with resolution. Everything works fine within my local private net but I also am WAN attached to another leg of our company. We each have our own domains and there is a two-way trust relationship set up.

The clients on my side point to the Mitel Firewall as their gateway and dns server. But I hand DHCP out from my PDC on the windows domain. They get their WINS info from that machine which also is aware of all of the WINS info on the WAN connected lan.

So from a command promt, I can for example PING OPSWEB and it will resolve and ping and a trace shows that it takes the proper route. However, if I try to use a web browser and type http://opsweb/ (which is a legitimate intranet web server) I get the response:

The requested URL could not be retrieved
While trying to retrieve the URL: http://opsweb.tti.net/

The following error was encountered:
    Unable to determine IP address from host name for opsweb.tti.net

The dnsserver returned:
    Name Error: The domain name does not exist.

This means that:
 The cache was not able to resolve the hostname presented in the URL.  Check if the address is correct.

How do I stop it from tagging my local fake network on and just resolving the way that the client machines do from the command line? Even HOSTS file entries don't work. Somehow the firewall asserts itself in front of the normal resolution chain of command.

Thanks for any help,

Kevin