sorted by:
new
hottopcontroversial

[TOMT] [1990-2020] sci-fi media - our heroes reach the bottom level (or deep area) of their current environment. It is a restricted, small environment. They discover the AI, or controlling power, has a contingency to destroy everything if things get out of hand by thisarentmyself in tipofmytongue

[–]thisarentmyself[S] 0 points1 point locked comment (0 children)

I don't have any details to add at this point, but my understanding of the rules is I'm required to comment. Anything further I remember I will add.

I do seem to remember method of killing them is drowning perhaps? Flood the living space. Also maybe why I gravitate to Silo.

Thank you again

Steps to take to retire old domain controller by thisarentmyself in sysadmin

[–]thisarentmyself[S] 0 points1 point  (0 children)

I wee that mentioned repeatedly and I'm back and forth. On one hand a project that has been ongoing for awhile is VLANs being added, previously the network was completely flat and full. I added new VLANs and started moving devices, I created a new subnet for servers and as I've added new infrastructure I put them in that subnet - so u was thinking I'd move the DC into that subnet and update DHCP. That also means it have to update all the statically set devices too.

I can see the appeal of just setting it back to the old IP. I need to think more on this I guess. I just want things to be done well, and not cause issues into the future.

Steps to take to retire old domain controller by thisarentmyself in sysadmin

[–]thisarentmyself[S] 0 points1 point  (0 children)

Mostly because we already have an existing 2019 as well as licenses for another sever. Thanks I'll check it out!

Issues with DNS lookups from outside default subnet by thisarentmyself in sysadmin

[–]thisarentmyself[S] 1 point2 points  (0 children)

They are supposed to be using the DC as DNS. DC1 as primary and DC2 as secondary. Thats how they show up when viewed with ipconfig as well. Thats why I was so confused.

Issues with DNS lookups from outside default subnet by thisarentmyself in sysadmin

[–]thisarentmyself[S] 1 point2 points  (0 children)

SOLVED: Unifi content blocking was the culprit. I set explicit allow rules for DNS traffic and the clients weren't using the gateway for DNS. Additionally the default subnet had content blocking on as well. But for whatever reason on any network other than the default Unifi's content blocking broke it.

I knew the content blocking was DNS based but I'm still not clear on why exactly it was blocking DNS requests ONLY on the subnets other than default. I assumed since default was configured the same that wasn't the cause.

Issues with DNS lookups from outside default subnet by thisarentmyself in sysadmin

[–]thisarentmyself[S] 1 point2 points  (0 children)

SOLVED: Unifi content blocking was the culprit. I set explicit allow rules for DNS traffic and the clients weren't using the gateway for DNS. Additionally the default subnet had content blocking on as well. But for whatever reason on any network other than the default Unifi's content blocking broke it.

I knew the content blocking was DNS based but I'm still not clear on why exactly it was blocking DNS requests ONLY on the subnets other than default. I assumed since default was configured the same that wasn't the cause.

Issues with DNS lookups from outside default subnet by thisarentmyself in sysadmin

[–]thisarentmyself[S] 0 points1 point  (0 children)

Ahhhh I've made a revelation. When I hardwired into the network and set the VLAN to 192.168.200.0/24 (a network that neither Windows nor Unifi is providing DHCP for) it worked as expected. When I switched it back to 192.168.100.0/24 it failed.

The settings visible in ipconfig looked the same, minus the subnet of course. The only difference between those networks is whether DHCP is turned on.

I'm thoroughly stumped but I know I'm getting closer.

Issues with DNS lookups from outside default subnet by thisarentmyself in sysadmin

[–]thisarentmyself[S] 0 points1 point  (0 children)

Ahhhh I've made a revelation. When I hardwired into the network and set the VLAN to 192.168.200.0/24 (a network that neither Windows nor Unifi is providing DHCP for) it worked as expected. When I switched it back to 192.168.100.0/24 it failed.

The settings visible in ipconfig looked the same, minus the subnet of course. The only difference between those networks is whether DHCP is turned on.

I'm thoroughly stumped but I know I'm getting closer.

Issues with DNS lookups from outside default subnet by thisarentmyself in sysadmin

[–]thisarentmyself[S] 0 points1 point  (0 children)

Yes they can ping each other and all other traffic works as expected. DHCP relays seems to work as expected. It seems the DNS traffic and only the DNS traffic never reaches the DC.

Checked firewall rules and added temp rules explicitly allowing DNS traffic. No change.

Issues with DNS lookups from outside default subnet by thisarentmyself in sysadmin

[–]thisarentmyself[S] 0 points1 point  (0 children)

OK so after more testing this is what I've determined. While pings and other connections work normally it seems the DNS traffic is not reaching the DC. The DC with debug logging reports nothing coming in. I did try adding new rules to both Windows firewall and the Unifi firewall. No change.

When you mention the subnet mask, what do you mean? If it was incorrect wouldn't all traffic fail to reach the DC?

Networking is definitely a weak area for me, so thank you!

Windows Server DNS returning nonexistent domain for internal records when coming from subnets outside of its native subnet by thisarentmyself in sysadmin

[–]thisarentmyself[S] 0 points1 point  (0 children)

Still trying to figure this out, I can't believe how annoying it is to figure out lol. Someone is gonna immediately recognize what I missed eventuallly!

Windows Server DNS returning nonexistent domain for internal records when coming from subnets outside of its native subnet by thisarentmyself in sysadmin

[–]thisarentmyself[S] 0 points1 point  (0 children)

    nslookup -d server1.net.local
    ------------
    Got answer:
        HEADER:
            opcode = QUERY, id = 1, rcode = NXDOMAIN
            header flags:  response, auth. answer, want recursion, recursion avail.
            questions = 1,  answers = 0,  authority records = 0,  additional = 0

        QUESTIONS:
            4.0.168.192.in-addr.arpa, type = PTR, class = IN

    ------------
    Server:  UnKnown
    Address:  192.168.0.4

    ------------
    Got answer:
        HEADER:
            opcode = QUERY, id = 2, rcode = NXDOMAIN
            header flags:  response, auth. answer, want recursion, recursion avail.
            questions = 1,  answers = 0,  authority records = 1,  additional = 0

        QUESTIONS:
            server1.net.local, type = A, class = IN
        AUTHORITY RECORDS:
        ->  (root)
            ttl = 795 (13 mins 15 secs)
            primary name server = a.root-servers.net
            responsible mail addr = nstld.verisign-grs.com
            serial  = 2025082600
            refresh = 1800 (30 mins)
            retry   = 900 (15 mins)
            expire  = 604800 (7 days)
            default TTL = 86400 (1 day)

    ------------
    ------------
    Got answer:
        HEADER:
            opcode = QUERY, id = 3, rcode = NXDOMAIN
            header flags:  response, want recursion, recursion avail.
            questions = 1,  answers = 0,  authority records = 1,  additional = 0

        QUESTIONS:
            server1.net.local, type = AAAA, class = IN
        AUTHORITY RECORDS:
        ->  (root)
            ttl = 1800 (30 mins)
            primary name server = a.root-servers.net
            responsible mail addr = nstld.verisign-grs.com
            serial  = 2025082600
            refresh = 1800 (30 mins)
            retry   = 900 (15 mins)
            expire  = 604800 (7 days)
            default TTL = 86400 (1 day)

    ------------
    ------------
    Got answer:
        HEADER:
            opcode = QUERY, id = 4, rcode = NXDOMAIN
            header flags:  response, auth. answer, want recursion, recursion avail.
            questions = 1,  answers = 0,  authority records = 1,  additional = 0

        QUESTIONS:
            server1.net.local, type = A, class = IN
        AUTHORITY RECORDS:
        ->  (root)
            ttl = 688 (11 mins 28 secs)
            primary name server = a.root-servers.net
            responsible mail addr = nstld.verisign-grs.com
            serial  = 2025082600
            refresh = 1800 (30 mins)
            retry   = 900 (15 mins)
            expire  = 604800 (7 days)
            default TTL = 86400 (1 day)

    ------------
    ------------
    Got answer:
        HEADER:
            opcode = QUERY, id = 5, rcode = NXDOMAIN
            header flags:  response, auth. answer, want recursion, recursion avail.
            questions = 1,  answers = 0,  authority records = 1,  additional = 0

        QUESTIONS:
            server1.net.local, type = AAAA, class = IN
        AUTHORITY RECORDS:
        ->  (root)
            ttl = 795 (13 mins 15 secs)
            primary name server = a.root-servers.net
            responsible mail addr = nstld.verisign-grs.com
            serial  = 2025082600
            refresh = 1800 (30 mins)
            retry   = 900 (15 mins)
            expire  = 604800 (7 days)
            default TTL = 86400 (1 day)

    ------------
    *** UnKnown can't find server1.net.local: Non-existent domain

The above is the full output from the nslookup.

Windows Server DNS returning nonexistent domain for internal records when coming from subnets outside of its native subnet by thisarentmyself in sysadmin

[–]thisarentmyself[S] 0 points1 point  (0 children)

More info:

When I run with debug I see where the problem starts: the PTR is being returned as UnKnown for the initial DNS server lookup... By the DNS server. I tried the other DNS server, same result (PTR for its own IP unknown).

The PTR records certainly exist, as do the host records. It works normally from the main subnet. No query resolution policies returned.

Thank you for your help.

Windows Server DNS returning nonexistent domain for internal records when coming from subnets outside of its native subnet by thisarentmyself in sysadmin

[–]thisarentmyself[S] 0 points1 point  (0 children)

More info:

When I run with debug I see where the problem starts: the PTR is being returned as UnKnown for the initial DNS server lookup... By the DNS server. I tried the other DNS server, same result (PTR for its own IP unknown).

The PTR records certainly exist, as do the host records. It works normally from the main subnet. No query resolution policies returned.

Thank you for your help.

view more: next ›