Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am trying to get a simple system running primarily as a learning tool. I am -->SO FRUSTRATED<-- I can hardly think straight.
Red Hat 8.
dlint ozco.home returns a warning about dual nameservers, but no other problems.
dig ozco.home seems happy. The answer section includes:
ozco.home. 86400 IN A 192.168.0.2
ozco.home. 86400 IN NS Silver.ozco.home
Silver.ozco.home. 86400 IN A 192.168.0.2
dig Silver.ozco.home gives me:
Silver.ozco.home. 86400 IN A 192.168.0.2
Silver.ozco.home. 86400 IN NS Silver.ozco.home.Silver.ozco.home.
I tried including named.conf and the zone files, but I don't have enough room. I will be elated to include whatever information I can to help figure this out.
I am trying to learn myself this here stuff. I am having huge trouble getting documentation on decoding strange messages. I don't even know if this is an error message or not! I do know that my windoze boxes can't see Silver, even with the simplest Samba.conf imaginable:
[global]
netbios name = Silver
Server string = "Hi, Yo!"
workgroup = OZCO
encrypt passwords = yes
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
Not only that, (Pete is right about your DNS problem), but DNS doesn't have anything to do with SMB any way. SMB uses NetBIOS names (dig is a DNS tool, not a NetBIOS tool).
You are indeed a guiness! I drink deeply of your wisdom!
Perhaps someone else has already suggested the concept of the pregnant server -- it is missing a period...Sorry. I couldn't help myself.
I know that Samba and DNS are only distant cousins, but as I said, I am trying to get this thing working as a learning tool. When Silver.ozco.home don't work, my windoze boxes can't see Silver.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
That's just it, though. SMB uses NetBIOS for naming. Even if your DNS is wrong, you'll still be able to reach it if you have NetBIOS setup correctly (run from nmbd, which is part of the Samba suite).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.