I always used to set DNS servers to the Google's 8.8.8.8 and 8.8.4.4 right after I log in to any network. However recently I found out I wouldn't get access to any site unless I set at my OS configuration to get default DNS server address connected to my campus network.
Is there any reason why a network configuration or network device make it impossible to a connected node to work normally with a custom dns server address? If so, how could I trick it?
Many organizations restrict direct access to external DNS servers by blocking DNS requests and replies at the firewall (i.e. they block UDP port 53). This is a common security practice to protect you from attacks. One such attack is a DNS spoofing attack, where an attacker will redirect your DNS queries to an "evil" name server. When you browse to www.mybank.com, the evil nameserver will return the address of a fake bank site, where they can fool you into revealing your login credentials.
The organization only allows its DNS server to make external queries, because presumably, it is better protected than your PC.
There is usually no way around the blocked port, and even if there were, its not my practice to subvert security policies. I'd be curious why you find the need to use a different DNS server than the one handed out via DHCP.
Most organizations don't want DNS traffic leaving the boundary or area of control so they can enforce policy on people within their organization. Local DNS servers have the capability to block certain domains or site classifications.
If so, how could I trick it?
In my organization, the most common trick people use to get around security policy is DNSCrypt, which uses HTTPS for DNS requests; making inspection nearly impossible. I use this technique at home, as well, so my ISP can't block any sites I go to.
Evading corporate policy probably isn't ethical, so I would highly advise against it.
Probably your campus network is filtering that DNS server. Or most probably is filtering any DNS except their ones. You can try this for example by using a tool to directly query a DNS (for example "nslookup - 8.8.8.8") and try with various DNS servers if it applies to them all.
The reason behind this is a control: by passing over their DNS they can filter out some name resolutions (ie. many countries use DNS filtering for some P2P sites such as TPB or Youtube and don't resolve it or resolve it to some IP they feel like) and of course logging (all the queries can be very easily logged to see what each PC in the campus network is trying to browse). Big brother in action!
If one wants to be less negative then you can see this also as a bandwidth optimization: since using their DNS and if their DNS is efficently doing caching this may prevent many requests going outside from the network.
If the DNS queries (ie. packets to tcp/udp ports 53 and so on) are filtered in your network then there is nothing (easy) you can do with it really.
