Home / user-128078

Zhuoyun Wei's questions

Martin Hope
Zhuoyun Wei
Asked: 2013-03-27 06:03:19 +0800 CST
  • 6

There is a dedicated server running Ubuntu Server 12.04.2. There are 4 useable IPs for this server: A, B, C, D. The server itself takes A.

The server is now running two VirtualBox guests, both with "Bridged adapter" network type. One guest is running Windows Server 2003, using IP address B. Another one is running Arch Linux (Live CD), using IP address C.

  1. In the Ubuntu host, the network is fine. I can apt-get and the downloading speed is good.
  2. In Windows guest, I can ping www.google.com in cmd.exe, but I cannot visit www.google.com in IE6.
  3. In Arch Linux guest, I can ping www.google.com in zsh, but curl -v www.google.com does not work. I can also telnet www.google.com 80, which means at least 80/tcp and 53/udp ports are working. (There is no iptables firewall on the server, actually.)
  4. In Arch Linux guest, I can even ssh to another machine! (using standard 22/tcp )
  5. In Arch Linux guest, I try to wget some https site, it stuck at "Connecting to XXX.XXX.XXX.XXX:443... connected".

I've tried changing --nictype1 setting for the VM and/or setting different MTUs in the guest OS, but the problem continues.

Can anyone help me?

Addtional information: When changing "Bridged adapter" to "NAT", the guest OS can curl www.google.com. Everything is fine. But since I need public IP, I have to use "Bridged adapter" for guest OS.

Addtional informationi 2: In guest OS with "Bridged adapter", I can ssh other host using 22/tcp, I can dig some domain using 53/udp, but I cannot wget or curl websites using 80/tcp or 443/tcp, but telnet www.google.com 80 or telnet www.google.com 443 is fine. When using "NAT" , everything is fine.

networking
Martin Hope
Zhuoyun Wei
Asked: 2012-09-21 06:16:11 +0800 CST
  • 3

I have a VPS with BIND set up. It works well for several months.

Recently I want to set up another DNS program to manage foo.example.org subdomain on this VPS. I've setup these in dns.he.net:

foo.example.org. IN NS vps.exmaple.org.
vps.example.org. IN A  xx.xx.xx.xx

Since BIND listens on 53/udp, I configured it to listen on port 5353 and in named.conf:

zone "foo.example.org" {
 type forward;
 forwarders{ 127.0.0.1 port 5353; };
};

I think this configuration will forward all queries for *.foo.example.org to the second DNS program. But when I test it...

On the VPS itself:

dig bar.foo.example.org @127.0.0.1 -p5353 works good.

dig bar.foo.example.org @127.0.0.1 works good.

On my laptop:

dig bar.foo.example.org @vps.example.org -p5353 works good.

dig bar.foo.example.org @vps.example.org works good.

dig foo.example.org @8.8.8.8 -t ns works good.

dig bar.foo.example.org @8.8.8.8 returns SERVFAIL.

Replacing 8.8.8.8 with other DNS servers gets same results and there is nothing wrong with TTL.

Is there anyone knows what's wrong with my configuration? Here is more info:

Other BIND9 configuration:

options {
  directory "/var/cache/bind";
  notify yes;
  allow-transfer { xx.xx.xx.xx; };
  dnssec-enable yes;
  dnssec-validation auto;
  auth-nxdomain no;    # conform to RFC1035
  listen-on-v6 { any; };
  recursion yes;
  allow-recursion { any; };
};

And, specifically, the "second DNS program" is iodine, which tunnels IP over DNS queries. I followed this guide to set it up behind BIND9: http://dev.kryo.se/iodine/wiki/TipsAndTricks#RunningiodinebehindBIND9

PS: I've tried another server with dnsmasq set up and use server=/foo.example.org/127.0.0.1#5353 to test. Still gets errors.

Could anyone help? Thanks in advance.

domain-name-system