Topic: DNS problem after update

[ch0nf1]

Hi! Until today I had a SME server perfectly working. I'm using it as a domain server, file server, dhcp server and dns server.

After updating today my server, I remarked that my workstations weren't running the login script anymore. When I tried to re-configure the domain in one of them, it gave me an DNS server error that it could find the address.
When I try to ping my server by name (Server Name) it doesn't respond. But when i ping it with the IP address (192.168.0.1) it responds without problem.
I tried many things from the forum but still can't find what is going on. When I try to ping internet sites by name, everything is okay.

I tried the command dnscache and tinydns and it gave me the following error:
dnscache: fatal: $IP not set or tinydns: fatal: $IP not set

To access the server-manager I must use the ip of the server.
I am still able to access the samba shares using the server IP.

Anyone can help me?

Thanks for your help!

[CharlieBrady]

As it says in large bright red letters when you post messages in this forum:


Don't report problems here.

If you have a problem after an update, please report it via the bug tracker.

http://bugs.contribs.org/

[compdoc]

I'm having the the same problem when you run tinydns, plus dns lookups are not working for rbls.

Unfortunately, for the life of me, I cant figure out how to search bugs.contribs.org for tinydns: fatal: $IP not set

That has to be the worst search gui I've ever had the bad luck to meet.

[CharlieBrady]

I'm having the the same problem when you run tinydns, ...

Sigh. As it says every time you post here - Don't report problems here - how can that be made clearer?

[CharlieBrady]

I tried the command dnscache and tinydns and it gave me the following error:
dnscache: fatal: $IP not set or tinydns: fatal: $IP not set

dnscache and tinydns are not commands designed to be run from the command line. Running them would not have helped you solve your problem, so there was no point in you trying to run them. You might just have well typed 'ls', or 'echo cross fingers".