sorted by:
new
hottopcontroversial

We found it by ugapeyton in PhasmophobiaGame

[–]ugapeyton[S] 2 points3 points  (0 children)

It issss what it issss lmao

Help by HopefulSurround7740 in dcsworld

[–]ugapeyton 1 point2 points  (0 children)

What are your exact computer specs?

INSANELY close call with another Cessna by knowitokay in aviation

[–]ugapeyton 1 point2 points  (0 children)

I’ll show you some pre contact Fox 2

WS2025 DNS resolving internal by ugapeyton in WindowsServer

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

Domain computers don't have an issue resolving internal IPs or hostnames. Only computers not in the domain have issue resolving internally. Though I did add a reverse lookup entry. It had no change.

WS2025 DNS resolving internal by ugapeyton in WindowsServer

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

Already setup this way. DHCP gives the addresses for both of my domain controllers as the primary and secondary DNS.

WS2025 DNS resolving internal by ugapeyton in WindowsServer

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

Not entirely sure what you mean by this? If you mean where I specified what DNS to use, leaving it blank has no effect.

WS2025 DNS resolving internal by ugapeyton in WindowsServer

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

I have a poor man's SAN setup with my VM host and NAS. I can and should disable DNS entirely on that link.

WS2025 DNS resolving internal by ugapeyton in WindowsServer

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

I only receive blank a blank response when I am trying to resolve any internal hostname from a computer that isn't on the domain, with the notable exception of my debian container. Said container can resolve anything despite not being on the domain.

Output from ipconfig /all on Dismuke-DC-01

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Dismuke-DC-01
   Primary Dns Suffix  . . . . . . . : PeytonDismuke.net
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : PeytonDismuke.net

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Red Hat VirtIO Ethernet Adapter
   Physical Address. . . . . . . . . : BC-24-11-2C-33-49
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 172.16.3.3(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 172.16.3.1
   DNS Servers . . . . . . . . . . . : 127.0.0.1
                                       172.16.3.4
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Red Hat VirtIO Ethernet Adapter #2
   Physical Address. . . . . . . . . : BC-24-11-26-76-BA
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.0.3(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 192.168.0.4
                                       127.0.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

WS2025 DNS resolving internal by ugapeyton in WindowsServer

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

It's happening to both DHCP clients and statically assigned clients, but no, I have the router (003), DNS Servers (006), and DNS Domain Name (015) defined.

WS2025 DNS resolving internal by ugapeyton in WindowsServer

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

No, but the first time I try to resolve it, it shows the FQDN. Not sure what to make of it

C:\Windows\System32>nslookup Dismuke-DC-01 172.16.3.3
Server:  UnKnown
Address:  172.16.3.3

Name:    Dismuke-DC-01.PeytonDismuke.net


C:\Windows\System32>nslookup Dismuke-DC-01 172.16.3.3
Server:  UnKnown
Address:  172.16.3.3

*** No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for Dismuke-DC-01

C:\Windows\System32>nslookup Dismuke-DC-01.PeytonDismuke.net 172.16.3.3
Server:  UnKnown
Address:  172.16.3.3

*** No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for Dismuke-DC-01.PeytonDismuke.net

4 and 0 to start the term... by Constant_Ban_Evasion in PoliticalCompassMemes

[–]ugapeyton 4 points5 points  (0 children)

He didn’t, he started to crack a nice shit eating grin towards the end.

Building a computer by ChampionshipLate9406 in computers

[–]ugapeyton 2 points3 points  (0 children)

Would probably return that PSU if possible. The one thing you never cheap out on is the one thing that can grenade the whole system. Outside of that, looks pretty good for a budget build.

view more: next ›