June 27, 201214 yr I'm unable to resolve any host outside of the lan or my hosts file. I think this started when I teamed my nics. Does anyone have any experirence on why external DNS is not working. DOn't skip the obvious I could be missing somthing and I'm frustrated.
June 27, 201214 yr What version of unRAID are you running? Where is your syslog? What EXACT commands are you executing to team your NICS. Without those, nobody can guess what is happening, or what you've done. Joe L.
June 27, 201214 yr Author I'm running 5.0RC5. NIC teaming settings. modprobe bonding modprobe e1000e ifconfig bond0 192.168.41.118 ifenslave bond0 eth0 ifenslave bond0 eth1 I've uninstalled DyDNS. Syslog attached. Thanks in advance. unraidsyslogJune272012.txt
June 27, 201214 yr See here: http://lime-technology.com/forum/index.php?topic=16887.msg186615#msg186615
June 28, 201214 yr Under Network Settings choose No but leave or add a DNS server address. This is usually your router.
June 28, 201214 yr Under Network Settings choose No but leave or add a DNS server address. This is usually your router. Yes. And this: ifconfig eth0 down
June 28, 201214 yr Author I checked and have two dns from ISP configured. What else am I looking for?
June 29, 201214 yr Author Yes I did. How should my go file look to bring this up a boot time? I have 2 e1000e nics and I am good with default settings.
June 29, 201214 yr See the link above. That config worked for me. The settings you provided do not include eth0 down or a default route. Try using the local router as the DNS address unless your sure that the router does not have a DNS server.
June 30, 201214 yr No DNS server. I want to use local DNS for internal hosts. Thanks What does this mean? I thought you had DNS addresses configured in the unRAID GUI.
June 30, 201214 yr Author Sorry no DNS server in router. I want to run a internal dns server and use a split configuration on my LAN. I'm good to go for now. I'm not going to reboot anytime soon. The default route may have been the fix. Don't know how that would have fixed the problem. I had reachability before. That's the only change I made and now my unraid server is resolving perfectly. Thank you for the help. Closed case.
June 30, 201214 yr Having both eth0 and bond0 (which includes eth0) up can cause routing issues. Only eth0 had a default route initially. There is no reason to have eth0 up when it is included in bond0. This problem may return unless eth0 is configured down.
Archived
This topic is now archived and is closed to further replies.