UDP Port forwarding does not remaps back source IP port.

Discussion in 'General Questions' started by VitaliiR, Nov 10, 2015.

  1. VitaliiR

    VitaliiR Bit poster

    Messages:
    4
    Hi.

    I have a MacOS X and I would like to use a DNS server located in a virtual machine outside of my host. I know that I could bridge the VM with my adapter, but it does not work for me (802.11x), also installing the server on the host machine is not an option as to it then must be done automagically via Vagrant and Ansible. So, I have installed Bind server onto Centos 6.6 with the following almost default config (commented out listen props, added google public DNS as a forwarder and allowed recursion for everyone).

    Code:
    options {
            #listen-on port 53 { 127.0.0.1; };
            #listen-on-v6 port 53 { ::1; };
            directory       "/var/named";
            dump-file       "/var/named/data/cache_dump.db";
            statistics-file "/var/named/data/named_stats.txt";
            memstatistics-file "/var/named/data/named_mem_stats.txt";
            allow-query     { localhost; };
            recursion yes;
    
            forwarders {
                    8.8.8.8;
            };
    
            allow-recursion { any; };
            allow-query-cache { any; };
    
            dnssec-enable yes;
            dnssec-validation yes;
            dnssec-lookaside auto;
    
            /* Path to ISC DLV key */
            bindkeys-file "/etc/named.iscdlv.key";
    
            managed-keys-directory "/var/named/dynamic";
    };
    And added 53 UDP & TCP forwarding rules in Parallels preferences.

    Executing `dig google.com @<VM IP>` I receive proper response, but unfortunately while making `dig google.com @<HOST IP>` with forwarding rules turned on, I receive the following response:

    Code:
    $ dig google.com @172.29.46.131
    ;; reply from unexpected source: 172.29.46.131#62958, expected 172.29.46.131#53
    ;; reply from unexpected source: 172.29.46.131#62958, expected 172.29.46.131#53
    ;; reply from unexpected source: 172.29.46.131#62958, expected 172.29.46.131#53
    
    ; <<>> DiG 9.10.3 <<>> google.com @172.29.46.131
    ;; global options: +cmd
    ;; connection timed out; no servers could be reached
    
    In the logs of my DNS server I see that query was successfully finished, no errors whatsoever.
    So I suppose this must be connected to how Parallels performs NAT forwarding.
    Executing `dig google.com @<HOST IP> +tcp` (with TCP flag on) I receive the response as expected, so forwarding for TCP must be working fine.

    Could someone please assist here?
    Any help would is greatly appreciated!

    Regards,
    Vitalii
     
  2. Manu@Parallels

    Manu@Parallels Guest

    Messages:
    259
    Hello Vitalii,
    We need you to submit a Problem Report and provide us with its ID number. Please follow this KB article to submit Problem Report:http://kb.parallels.com/9058
     
  3. VitaliiR

    VitaliiR Bit poster

    Messages:
    4
    Hi Manu,

    I've created a Problem Report #82487707.

    Regards,
    Vitalii
     
  4. Elric

    Elric Parallels Team

    Messages:
    1,712
    Thank you for the report, we have reproduced the issue locally. If you are interested, I can send an updated version of network component when this will be fixed (I expect within one week)
     
  5. VitaliiR

    VitaliiR Bit poster

    Messages:
    4
    Hi Elric,

    Thank you very much! I'd really appreciate that.

    Regards,
    Vitalii
     
  6. Elric

    Elric Parallels Team

    Messages:
    1,712
    Hi VitaliiR, I've sent you a private message. Not sure whether email notifications are delivered, so just making a note here
     
  7. VitaliiR

    VitaliiR Bit poster

    Messages:
    4
    Hi!

    After updating to 11.1.2 (32408) I found this to be fixed and working great. Thank you very much!

    Regards,
    Vitalii
     

Share This Page